Archive Magazine CD 1995/Archive Magazine CD 1995.iso/text/hints/volume_02/issue_07

Text File | 1995-02-16 | 29.8 KB | 902 lines

2.7
•   BBC winchester on Archimedes!! Alan Glover saysÉ I have got it to
work on the i/o podule under RISC-OS. Here’s what you do: from the
!65Host directory:
2.7
*RMLOAD !RunImage
2.7
*CACHEROM 0 dnfs
2.7
*CACHEROM 1 ARFS
2.7
*CACHEROM 2 <>.ADFS130
2.7
*EMU.
2.7
Note: Must be ADFS 130 − i.e. a B/B+ version  and you must find an image
of this yourself as it is not provided with RISC-OS. To use the
Archimedes’ ADFS type *ARFS.
2.7
The winchester is connected to the 2 MHz bus (theoretically 1 MHz!) on
the I/O podule as it would be on a BBC.
2.7
•   Configuration problems in Art Nouveau − If you select ‘Configure
machine’ from the opening menu when you have already configured the
machine, you lose your old configuration when you quit and you are left
with Art Nouveau’s own configuration. This is because it doesn’t keep
track of whether you have already configured it. I was lucky − I had
written a program long ago that translates a *SPOOLed *STATUS into a
load of *Configure’s and I keep a copy of this spool on my hard disc at
all times. You have been warned. Martyn Lovell.
2.7
•   Graphic Writer with a Star SG-10 − If you can have one complaint
about Graphic Writer (apart from the manual) it’s the printer support. I
own a Star SG-10 and am trying to let Graphic Writer use it to the full.
The Star has an NLQ character set, but this cannot be combined with any
other text style except underlined. So what I want is to adapt the
printer driver so that it would normally print NLQ and for the other
effects resort to draft printing. For this, I used the Printcon program
and gave the following codes:
2.7
Initialisation:
2.7
ESC “@”
2.7
ESC “G”
2.7
ESC “4”
2.7
Which resets the printer, turns on double-strike (gives better bold, but
you may omit it) and NLQ. Make sure the printer is in IBM mode.
2.7
For configuration (leave the rest the same as a FX80):
2.7
Plain:     27,70,27,52
2.7
Bold:      27,53,27,69
2.7
Italic on: ESC “I”,1
2.7
Italic off:ESC “I”,0
2.7
Note that the input routine of the printcon program doesn’t accept two
“ESC” sequences on one line, but it accepts two 27’s. The italic codes
are different from an FX80. In fact, FX80 compatibility turns out to be
somewhere in between the “Star” and “IBM” modes of the Star SG-10. The
trick is the plain and bold codes. When Graphic Writer finds a “Bold”
code it now also sends an NLQ-off code to the printer, which in effect
makes the printer print in draft, emphasized and double-strike, the
latter being already set at initialisation. (Yes, it is confusing, isn’t
it?!) This makes it possible to mix NLQ, bold and italic-bold in the
text. However, you can’t use italics or super/subscript without bold.
These just print in normal NLQ.
2.7
The same method should apply to other printers which can’t do everything
in NLQ.
2.7
Another tip on Graphic Writer is that you should always make any graphic
as big as possible, i.e. use the whole graphic area, however small you
want the picture to be. This makes page composition a lot easier and
also causes less problems with distortion when rescaling.
2.7
•   Interrupt module − The interrupt module by Steve Hoare (Archive 2.6
p44) is very useful especially, as he states in his article, with First
Word Plus for creating directories etc. However there is a problem
associated with *interrupt 0. This is that the pound key also generates
ASCII 0 (a bug in OS1.2 I think) which means that every time you type a
‘pound’, the interrupt module takes over and opens up the OS window.
However, <ctrl-O> is unused by First Word Plus, so I use *interrupt 15
instead.
2.7
The module also comes in handy when using a comms program to check on
filenames, *type logfiles etc, but there is an enhancement that I think
would make it more useful still. While in the OS window, it is possible
to type <ctrl-Z> to open up the text window to the full screen which is
handy, but on exit (in a WIMP program) only the top half of the screen
is restored. If the source code could be modified to issue a redraw
request for the whole screen it would be an improvement. Having looked
at the code, it should be easy to do. Any offers?
2.7
•   Memory shortage on Logistix and First Word Plus − To get round the
‘out of memory’ snag which seems to turn up so often with First Word
Plus and Logistix, if you have the 1.20 PC emulator, use the PC.PC
startup routine first and then, instead of using the MS.DOS disc, insert
Logistix instead and <reset>. <Ctrl-break> will then autoboot Logistix
with a whole 275k of memory free to use.
2.7
•   Mitsubishi Disc Drives − Here are a number of points to bear in
mind, writes Vic Budd, when adding external disc drives. If, after
considering these, you feel competent to carry out the work, go ahead.
If not, it is prudent to entrust the work to an experienced operator to
avoid frustrations and disappointments.
2.7
There are different circuit board layouts, but the basic checks on the
drives are the same.
2.7
1.   Remove link MS if made and change to adjoining position MM.
2.7
2.   Remove link IU if made and discard it. On some drives there is no
removable link. However, there is a circuit board foil link, DI, near
the data cable edge connector, which is connected to pin 2, and this
should be cut in these instances.
2.7
3.   Move drive selector link to position 1, 2 or 3 according to which
command you wish it to respond. (This assumes that the internal drive is
to be 0).
2.7
4.   The resistor pack should be in place. On some drives this consists
of a single plug-in IC type device, whilst on others there is a row of
DIL pins which should have shorting links inserted.
2.7
5.   Make sure the data cable is correctly orientated − it will need to
be at 180 degrees compared to the three and a half inch drive
connectors.
2.7
6.   If, as I do, you wish to run a second three and a half inch
external drive and a five and a quarter inch drive, the connecting cable
will, of course, need to be turned through 180 degrees to connect the
drives together.
2.7
7.   If you decide to use the Archimedes’ power supply, check the
connections carefully before attaching the cable connectors, making
quite sure you do not get the 12v and 5v leads confused.
2.7
If you do all these things correctly, you too should have no problems
with the Beebug lead and will be able to access drives A, B and C under
the PC Emulator, as well as 0,1, and 2 under ‘native’ Archimedes.
2.7
•   Moving the pointer when it is not linked to the mouse can be greatly
simplified by using the POINT TO x%,y% command which does exactly what
is needed (note that you must unlink the pointer from the mouse first
with MOUSE ON 129). Details are in the User Guide and under HELP POINT.
Having looked at the relevant part of the PRM, it appeared to be
impossible to do this, so I decided to have a rummage around in the
BASIC module. This resulted in the discovery of some undocumented calls!
Basically these are extensions of OSWORD &15 whereby putting &05 instead
of &03 at R1+0 causes the pointer position to be set instead of the
mouse position (see PRM p.133). Also, values of &04 and &06 appear to
read the mouse and pointer positions respectively, though the code to
read the mouse position contains a fatal bug in Arthur 1.2 and cannot be
used! In theory it might be possible to patch it with a copy of the
UtilityModule in RAM but this module refuses to be RMKILLed. Martin
Simmons
2.7
•   Problems with *UP − If you are having problems (as expressed in the
Help Section last month) with *UP or the use of ^ in a pathname, it is
probably because of a bug in the ADFS. The problem occurs when a
directory is renamed. The ADFS does not seem to keep track of it
properly. The solution, apparently, is to do a *COMPACT on the disc.
2.7
•   Repton 3 again (Philip Armstrong) − I’ve got a few more comments on
Repton 3. Firstly I hope that no one saved the new characters and maps
onto the original disc. I have found that occasionally, the maps have
been corrupted and thus rendered impossible. If you find a screen that
you can’t do then check it with the original version. For those people
that can’t get to grips with the array of different characters, create a
second disc with all the files using a standard set of characters. This
makes the screens easier to complete. I have included on the monthly
program disc, the new characters that I use. They are not brilliant, but
a distinct improvement on the original set. Superior Software only state
that characters and maps cannot be used for commercial exploitation, so
it is OK for us to distribute in this way. There is also a simple
program to merge maps and my characters. Also, if you cannot stand the
tune that accompanies the loading program of Repton, then change *tune1
to *tune0 in the “config” file.
2.7
Here is a list of Passwords for Repton 3. Sorry it’s not complete, but I
do have other things to do. If anyone can do screen E of WORK
(p=scratch), I’d be pleased to hear from them because it looks imposs
ible and I have checked it against the original. I suspect a transporter
has been defined wrongly.
2.7
A   Prelude   B   Rescind   C   Periwig   D   Mortify      E   Forsake
F   Gratify   G   Thistle   H   Spangle
2.7
A   Toccata   B   Nocturn   C   Liberal   D   Inspect      E   Delight
F   Botanic   G   Vitriol   H   Sacking
2.7
A   Finale   B   Yardarm   C   Zealous   D   Without      E   Aviator
F   Elderly   G   Juniper   H   Crimson
2.7
A   America   B   Herbage   C   Kitchen   D   Outcast      E   Quarter
F   Untwine   G   Tremble   H   Strange
2.7
A   Arctic   B   Kinetic   C   Gondola   D   Lozenge      E   Rotunda
F   Frontal   G   Younger    H
2.7
A   Orient   B   Organic   C   Armhole   D   Visible   E   Neglect   F
Biplane   G   H
2.7
A   Oceans   B   Distain   C   Mundane   D   Eclipse   E   Warning   F
G   H
2.7
A   Africa   B   Quickly   C   Zigzags   D   Closely   E   Panoply   F
Bonfire   G   H
2.7
A   Baby   B   Startle   C   Measles   D   Granite   E   WhimperF
Cushion   G   Alimony   H   Utensil
2.7
A   School   B   Qualify   C   Knicker   D   Dynamic   E   Tendril   F
Lanyard   G   Vinegar   H   Yaskmak
2.7
A   Teenage   B   Eternal   C   Whisper   D   Feather   E   Rhubarb   F
Jasmine   G   H
2.7
A   Work   B   Inverse   C   Parapet   D   Elegant   E   Scratch   F   G
 H
2.7
A   Oap   B   Jackdaw   C   Rupture   D   Archery   E   Figment   F
Natural   G   Tonight   H   Brigade
2.7
A   Prehist   B   Dormant   C   Mineral   D   Varnish   E   Dashpot   F
Lobelia   G   Upright   H
2.7
A   Egypt   B   Lobster   C   Tabloid   D   Achieve   E   Gristle   F
Deceive   G   Scalpel   H
2.7
A   Victori   B   Earnest   C   Pervade   D   Violent   E   Bashful   F
Magnify   G   Wrought   H   Horizon
2.7
A   Now   B   Charity   C   Funeral   D   Justify   E   Naughty   F
Isolate   G   Radical   H
2.7
A   Future   B   Primate   C   Mustang   D   Iterate   E   F   G   H
2.7
•   Shared C Library − Users of release 2 of ANSI C might like to know
how to use the Shared C Library which is included on the disc but which
does not seem to be documented in the User Guide. Normally, the AOF
file, generated by compiling the C source, is linked with the C ANSI
library file, $.ARM.CLib.O.AnsiLib. This produces an image file which
can be executed directly by *RUNning it. This image file tends to be
quite long as large port-ions of the C ANSI library are incorporated in
it.
2.7
On the C disc, is a file called $.Library.CLib which contains the C ANSI
library in the form of a relocatable module. The interface between the
user program and this Shared C Library module is a small file called
$.ARM.CLib.O.Stubs which simply defines each ANSI library function as a
SWI which is then recognised by the library module.
2.7
As an example of the use, try the following. Mount your working copy of
the C disc and enter directory $.ARM.CBench. Now compile the source file
C.HelloW using the -c option so as not to invoke the linker:
2.7
*CC HelloW -c
2.7
Now link the resulting AOF file with the Stubs library:
2.7
*Link -o HelloW O.HelloW $.ARM.CLib.O.Stubs
2.7
Next load the Shared C Library module:
2.7
*RMLoad $.Library.CLib
2.7
And finally run the program:
2.7
*Run HelloW
2.7
Note that an image file generated in this way is not truly stand-alone
as it needs the Shared C Library module to be loaded in order for it to
run (but then again many programs need the Floating Point Emulator to be
loaded in order to run). A big advantage is that the image file is very
much smaller than it would be if it had been linked with the ANSI
library in the normal way. One can envisage several C programs multi
tasking under RISC-OS, sharing the resources of the Shared C Library.
2.7
It should be noted that the Arthur-specific functions declared in the
ArthurLib header file are not incorporated in the Shared C Library. If
your program uses these functions you must include
$.ARM.CLib.O.ArthurLib at the linking stage. So try the following:
2.7
*CC Balls64 -c
2.7
*Link -o Balls64 O.Balls64 $.ARM.CLib.O.Stubs $.ARM.CLib.O.ArthurLib
2.7
*Run Balls64
2.7
Provided the Shared C Library module is loaded, the program should run
normally. John Morley
2.7
•   Sprite Animation − There have been many articles relating to the use
of Sprites on the Archimedes. These have covered the use of PLOT &ED,X,Y
to display a Sprite in its defined colours at point (X,Y) and the use of
a Mask to allow a background to appear through the ‘unused’ parts of a
sprite. They have also shown the use of Exclusive OR plotting using GCOL
11,0 to allow the sprite to be moved over any coloured background.
2.7
The EOR solution to this last problem, of moving a multi-coloured sprite
over a multi-coloured background, does work, but unless a great deal of
thought is given to palette selection, the sprite does not retain its
defined colour during movement.
2.7
Many games will require the facility to define a sprite in specified
colours, with a mask and to move it still retaining those colours rather
than those produced by EOR.
2.7
A solution is to use the standard Move/Display/Erase in a loop but not
to use EOR. The following algorithm does this :
2.7
1   Define the sprite ‘MySprite’ with a mask (using SEDIT on the Welcome
Disk).
2.7
2   Determine the size of ‘MySprite’. This may be known but a SYS call
does it for you.
2.7
LOOP
2.7
3   Determine the position where ‘MySprite’ is to be plotted.
2.7
4   Grab a sprite ‘Temp’ from the screen at this position the same size
as ‘MySprite’.
2.7
5   Plot ‘MySprite’ with the mask.
2.7
6   Plot the grabbed sprite ‘Temp’ to ERASE ‘Mysprite’.
2.7
ENDLOOP
2.7
The following program demonstrates this :
2.7
 10 REM > SpritePlot
2.7
 20 REM Copyright Ian Smith
2.7
 30 REM March 1989
2.7
 40
2.7
 50 REM An example program to show
2.7
 the use of sprites moving
2.7
 60 REM across a multi coloured
2.7
 background by grabbing an area
2.7
 70 REM of screen as a sprite and
2.7
 then using it to overwrite the
2.7
 80 REM moving sprite.
2.7
 90
2.7
100 MODE 15  :REM Works in other
2.7
 modes
2.7
110 T$=“Temp”  : REM Will be the
2.7
 sprite grabbed from screen
2.7
120 M$=“MySprite”  : REM A masked
2.7
 sprite created with SEDIT
2.7
130 *SLOAD !Sprites
2.7
140
2.7
150 SYS &2E,40,,T$ TO ,,,W,H :REM
2.7
 Find size of sprite to grab
2.7
160       : REM W)idth and H)eight
2.7
170 PROCDrawBackground  : REM Draw
2.7
 a Multicoloured background
2.7
180 PROCTitle:REM and put titles on
2.7
190
2.7
200 REPEAT
2.7
210  REM ****** MOVE ******
2.7
220  MOUSE X,Y,B
2.7
230  SYS &2E,16,,T$,1,X,Y,X+W*2,
2.7
Y+H*4  : REM Grab sprite
2.7
 from screen
2.7
240
2.7
250  OSCLI(“SCHOOSE ” + M$ ) :REM
2.7
 Select original sprite
2.7
260
2.7
270  REM ****** DISPLAY ******
2.7
280  GCOL 8,0 :REM Now plot it with
2.7
 its mask
2.7
290  PLOT &ED, X,Y   :REM at the
2.7
 mouse position
2.7
300  PLOT &ED,900,800  : REM and
2.7
 display it in rectangle
2.7
310
2.7
320  WAIT:WAIT  : REM Synchronise
2.7
 output
2.7
330
2.7
340  OSCLI(“SCHOOSE ” + T$) :REM
2.7
 Now plot the grabbed sprite
2.7
350
2.7
360  REM ****** ERASE ******
2.7
370  GCOL 0,0
2.7
380  PLOT &ED,X,Y : REM at the same
2.7
 place
2.7
390  PLOT &ED,1000,800  :REM and in
2.7
 its rectangle
2.7
400 UNTIL B=7      : REM 3 buttons
2.7
 terminates
2.7
410 END
2.7
420
2.7
430 DEF PROCDrawBackground
2.7
440 GCOL 3 : RECTANGLE FILL 0,0,
2.7
300,300 : REM Just a
2.7
 couple of
2.7
450 GCOL 4 : RECTANGLE FILL 50,50,
2.7
50,50 : REM rectangles and
2.7
460 GCOL 12:CIRCLE FILL 800,400,200
2.7
: REM circles
2.7
470 GCOL 5 :CIRCLE FILL 600,300,100
2.7
480 OSCLI(“SCHOOSE ” + M$)
2.7
490 PLOT &ED,75,90 : REM and the
2.7
 sprite
2.7
500 ENDPROC
2.7
510
2.7
520 DEF PROCTitle
2.7
530 GCOL 1
2.7
540 RECTANGLE 900-2,800-4,W*2+4,
2.7
H*4+8 :REM Draw rectangles
2.7
550 RECTANGLE 1000-2,800-4,W*2+4,
2.7
H*4+8 : REM in which sprites
2.7
560 PRINT TAB(53,2);“S P R I T E S”
2.7
  : REM are displayed
2.7
570 PRINT TAB(52,3);“original
2.7
 grabbed“
2.7
580 PRINT TAB(0,1);“SPRITE
2.7
DEMONSTRATION : use mouse
2.7
 to move sprite“
2.7
590 ENDPROC
2.7
Comments on the program
2.7
PROCDrawBackgound sets up a background to move over.
2.7
PROCTitle puts text and a couple of rectangles on the screen
2.7
150   uses a SYS call to find the Width and Height of ‘MySprite’. This
is needed so that the right size ‘Temp’ can be grabbed. (See PRM pp
429,433.)
2.7
230   grabs the sprite from the screen using a SYS call. Note the *2 and
*4 to compensate for screen MODE 15. You’ll need to change this for
other resolution modes.
2.7
250   selects ‘MySprite’
2.7
280   selects the Mask Plot option GCOL 8.
2.7
290   plots the sprite at the Mouse selected point
2.7
300   plots the sprite in a rectangle to show its original colours.
2.7
340   selects ‘Temp’
2.7
380   plots ‘Temp’ effectively erasing ‘MySprite’
2.7
390   plots ‘Temp’ in its rectangle. The effect of 390 has an interest
ing side-effect. When you run the program move the sprite over the
rectangle! See what happens!
2.7
The program ‘SpritePlot’ and the sprite file ‘!Sprites’ are on this
month’s disk but you can use the program by keying it in and also
creating a masked sprite in mode 15 using SEDIT and saved as !SPRITES.
2.7
The program can obviously be modified to run in other modes. The flicker
on the sprite could be removed by modifying the program to plot only if
the mouse has been moved. Ian Smith
2.7
•   Star-Trader Cheats − Here are some ideas and cheats for
‘StarTrader’. It is an excellent game, all the more impressive when you
consider it is written in BASIC!
2.7
Load the main game and enter the EDIT editor. (The main game file is
‘$.Resouces.StarTrader. StarTrader’.) You can alter as many as the
following as you like to make the game a bit easier to get into;
2.7
Line 290 change to: SUN=1 for a SunBurst
2.7
   DEATH=1 for a DeathBlossom
2.7
   CELL=1 for a super energy cell
2.7
   ENG=3 for the most powerful engines (Note ENG=2 & ENG=1 are available
as well)
2.7
   NUMPT=10 for the number of photon torpedoes. Having 10 doesn’t spoil
the display!
2.7
Line 390 change CRD to the number of credits you want (STDA is the
stardate)
2.7
Line 420 change MAXHOL to the size of the hold you want fitted.
2.7
Note: DAMCAP is used in Line 13570 to calculate the remaining hold
capacity.
2.7
PRC() holds the value of each of the tradegoods you are carrying CTOTAL
is the total weight of cargo you are carrying at the moment (also used
in 13570)
2.7
The messages you occassionally get when transporting down to a planet
are held in code. If you want to see them, then type the following
changes in immediate mode.
2.7
LOAD “StarTrader”
2.7
DELETE 0,39349
2.7
DELETE 39560,39580
2.7
DELETE 39640
2.7
DELETE 39650,39690
2.7
39351 DIM CMG$(20)
2.7
39554 FOR T=0 TO  20
2.7
39651 NEXT
2.7
PROCCLUE (If <ctrl-B> is used first, the messages can be sent to a
printer.)
2.7
There is a 50:50 chance of getting a clue on any planet landing. 16
messages have a 95% chance of being called, the other 4 messages only
5%. The rumour sends you to a randomly chosen planet! Some messages are
tradehints, some are adverts for other games(!) and a couple are very
useful clues to the solution of the puzzle.
2.7
The planets on which the segments are found and the code are chosen at
the creation of the universe stage. RUN the game, then immediately save
it. TYPE in CHEAT4 to get a list of planet numbers where the segments
are. CHEAT4 also prints out the code letters. These are held in the
array ZTX()
2.7
 10 REM >CHEAT4
2.7
 20 DIM PKLR(800),GR(800),ANAME$
2.7
(800),TYP(800),SS(800),PO(800)
2.7
,STARSS(120),PX(120),PZ(120), PC(9),SP(9),PRC(13), UNI(120,12),ZTX(8)
2.7
 30 BB=OPENIN(“:1.xxxxx”):REM
2.7
 change xxxxx to name of
2.7
 SaveGame file
2.7
 40 INPUT# BB,SUN,DEATH,CELL,ENG,
2.7
 FS, PS,SS,AS,PTD,PSD,DAMCAP,HD, TE,NUMPT,PE,EPS,STDA,CRD,PN,SY
2.7
 50 FORT=1TO800:INPUT# BB,PKLR(T),
2.7
 GR(T),ANAME$(T),TYP(T), SS(T),PO(T):NEXTT
2.7
 60 FORT=1TO120:INPUT# BB,SARSS(T)
2.7
 ,PX(T),PZ(T):NEXTT
2.7
 70 FORT=1TO9:INPUT# BB,PC(T),SP(T)
2.7
:NEXTT
2.7
 80 FORT=1TO13:INPUT# BB,PRC(T)
2.7
:NEXTT
2.7
 90 FORZ=1TO119
2.7
100 FORT=1TO12:INPUT# BB,UNI(Z,T)
2.7
:NEXTT
2.7
110 NEXTZ
2.7
120 FORT=1TO8:INPUT# BB,ZTX(T)
2.7
:NEXTT
2.7
130 CLOSE# BB
2.7
140 FOR LOOP=1 TO 9:PRINT PC(LOP),
2.7
SP(LOOP)’:NEXT:REM planets
2.7
150 FOR LOOP=1 TO 8:PRINTCHR$(64+
2.7
ZTX(LOOP)):NEXT:REM code
2.7
You get a nice fanfare when you collect a segment. The percentage
chances reported during a scan can be as low as 45% or as high as 90% on
a planet which actually has a segment.
2.7
If you have two drives, it is quite easy to use drive 1 as the GameSave
drive (as in the program above). Just change (input$) in Lines 3770,
4020 and 4050 to (“:1.”+input$). Dave Kent
2.7
•   TV output from Archimedes? − It is possible to connect a TV to an
Archimedes, though only in monochrome and via a video.  Connect a wire
(co-ax) from a phono plug plugged into the Archimedes mono video socket
to pin 20 (centre core of Co-ax) and any one of the many 0V lines (i.e.
connect the braid screen to 0V) on a SCART plug. This means that it only
works on video machines with a SCART socket on them (if no SCART socket,
then connect to VIDEO IN via a phono or BNC plug). This also means that
you can make demo videos and stuff by taping the pictures. Sound can be
connected to pins 2 and 6, I think, never tried it! (See Archive 2.2 p
6)  Does anyone now how to convert the Archie mono out to colour?
Plugging the Archie SCART cable to the video doesn’t work! Oliver
Cornes.
2.7
•   Using First Mail − At first, I regarded First Word Plus as a very
ordinary word processor. The need to keep reformatting with <f12> seemed
to be a step backward. However First Mail changes the picture for me.
Here are one or two ideas on how to use First Mail for handling ordinary
day-to-day cor-respondence.
2.7
I “merge from” a file carrying my letterhead. In fact I have a few
different letterheads for different purposes. In addition to the
letterhead my “from” file has the following First Mail commands:
2.7
longdate
2.7
input “address file?”, address
2.7
input “text file?”, text
2.7
includefile dat.address
2.7
Dear
2.7
includefile doc.text
2.7
includefile dat.address
2.7
(The bits in italic that should be in light type. It is not obvious
which the light bits should be; but see the note on p. 206 of the First
Word Plus manual.)
2.7
The system asks me for an address file and then a file containing the
text of the letter, both of which it merges with the letterhead. The
second printing of the address comes after a hard page break. Since I
specify pauses on page breaks, this allows me to remove the letter from
the printer and replace it with the envelope (or sticker) for the second
address to be printed on that. I can cancel this when I do the draft
copy, which I keep for my own files. I save my letter texts in the doc
directory and addresses in the dat directory. This allows me to use the
same name for both if that is more convenient.
2.7
Incidentally I use a brother daisywheel for most of my letter quality
printing; and I have configured the driver to print my letterhead in
bold red. A nice feature of First Word Plus is that you can have several
drivers for the same printer if you give them different names. Not only
that, but with a daisy-wheel you can have two configurations on the same
driver by making the NLQ configuration different from the draft
configuration, though of course, the terms draft and NLQ will have no
real meaning for a daisywheel.
2.7
There are some errors in the Brother driver supplied, by the way; so
check with the manual, especially if you are Danish or are in the habit
of using some of the more obscure symbols. The First Word Plus manual is
a bit vague about full pathnames, too. For instance, to install a
different default printer you have to type, say,
2.7
*copy 1wp.cfg.epson_fx resources.
2.7
1wp.1wp_print
2.7
I find the First Word Plus file window most useful for exploring discs.
If you click on the window exit symbol you get the parent directory.
Clicking on a directory name in the window lists that directory in the
window as well as selecting it in the directory slot. Glyn Emery.
2.7

2.7
We begin a new section this month to help you get to grips with RISC-OS.
When you buy RISC-OS, you get a disc full of information from software
houses (see list below) about how to get their software running under
RISC-OS, but I suspect that because RISC-OS is so new, there will be
lots for us all to learn − hence this column.We really need a volunteer
to be the editor of this corner − someone to whom I can send all the
info and who will then collate it, check it and regurgitate it to me
(preferably via Eureka II for speed). Anyway, Mike Harrison, Matthew
Treagus, Keith Milner and Ting Kuei start us off.
2.7
•   Flashing screens − I’ve just got hold of the release RISC-OS User
Guide and noticed that it does not seem to mention the fact that in
modes 21, 24 and 28, the screen blanks when accessing floppies, due to
the high DMA rate. I’m sure many dealers will get calls from worried
users who think that fitting RISC-OS has damaged their machine because
of the screen flashing on and off!
2.7
•   Logistix − Logistix users must replace the Floating Point Emulator
in the Library of the Log-istix Disc (version 2.50) with the later one
which is supplied with RISC-OS, i.e. FPE version 2.60. It can also be
found on the ABC Compiler Disc. If this is not done Logistix, will not
run correctly.
2.7
•   TWIN − If, like me, you are annoyed at the delay in loading TWIN
when editing programs, especially with BASIC using TWINO8, make an Obey
file that does the following :
2.7
Set Run$Path Ram:,<Run$Path>
2.7
Copy Twin Ram:Twin f~c
2.7
(Ensure that your configured RamFS size is big enough first!). After
running this, Twin will be instantly loaded from Ram Disk. You can of
course also include in the file a *Key command to define your favourite
function key to call Twin, e.g.
2.7
 Key 1 |UTWINO8|M
2.7
For BASIC. The |U deletes any crud which may have been on the command
line before you hit <f1>.
2.7
•   Virsuses on RISC-OS!!! − I wonder how many people will look at this
in panic. Don’t worry. There is a virus on RISC-OS, even before it is
released, but it is totally harmless. In fact it is quite fun. First, a
brief description of how most viruses work:
2.7
Most business machines load their operating system from disk. So, in
order to ‘virus’ one of these machines, the offending program just
becomes part of the operating system in some way. It copies itself onto
other discs with operating systems on and soon every copy of the OS you
have is “infected”.
2.7
On a sensible computer, such as the Archimedes(!) the operating system
is on ROM, and cannot be altered! Thus if someone decides to write a
virus program, once it is detected, turning the machine off will remove
it. It is, however, possible to install a virus on other files on disc.
This is much more difficult to do, is easier to detect and easier to
remedy. For instance, the !BOOT file is a common file to be found on a
disc, and a virus could conceivably attach onto this, although it would
be very difficult since every !BOOT file is different.
2.7
I will not disclose how the RISC-OS virus installs itself as it will
only encourage people to write viruses. I will say, however, that once
detected, it is ((very simple)) to remove it with no after effects. If
the virus (which actually originates from Acorn!) appears on your disc,
not much actually happensÉ or at least it appears that way. You are
using the desktop as normal and suddenly, a small fish appears on the
screen and swims across, behind all the windows, leaving a trail of
bubbles which rise to the top of the screen and disappear. Several more
fish swim backwards and forwards on the desktop until the machine is
reset. This virus is totally harmless, the only ill effect is to use up
a bit of processor time! In fact, I have installed it deliberately as it
is quite relaxing!
2.7
Another virus we have heard of is the FF8 virus which adds itself to
filetype FF8 files. It displays a message and prevents the affected file
from running on the 13th of the month.This it is a real pain if you are
not careful, i.e. if you forget to turn the computer off before running
a new program!  There is a detector program available (downloadable from
area 2 on Eureka II) but it will only check for the existence of the
virus and will not destroy it.
2.7
•   Manuals − Q: When RISC-OS is available, does it mean that the
manuals I purchased are outdated or will Acorn publish a cheap edition
to add to it?
2.7
A: The bulk of the PRM remains correct, however there is a wealth of
brand new information and a new PRM will be out in due course, probably
in three volumes!
2.7
The following firms have provided help on RISC-OS compatibility. The
information is on the Support Disc that comes with RISC-OS.
2.7
Abacus Training Ltd
2.7
Ace Computing
2.7
Acorn Computers Ltd
2.7
AVP Computing
2.7
Cambridge Micro Systems Ltd
2.7
Clares Micro Supplies Ltd
2.7
Colton Software
2.7
Dabs Press
2.7
Dixon and Dixon
2.7
Emmerich (Berlon) Ltd
2.7
GEM Electronics
2.7
Intelligent Interfaces Ltd
2.7
Institute of Ophthalmologists
2.7
Lendac Data Systems Ltd
2.7
Lingenuity (Lindis International Ltd)
2.7
Magenta Research Ltd
2.7
Maze Technology
2.7
Meadow Computers
2.7
Minerva Systems Ltd
2.7
Mitre Software Ltd
2.7
Oak Professional Software Ltd
2.7
Silicon Vision Ltd
2.7
Watford Electronics Ltd